Data counter measures

ABSTRACT

Techniques to block unwanted third party calls are disclosed. In various embodiments, an indication is received that third party code included on a web page is attempting to write to the web page content associated with an unauthorized third party call. The unauthorized third party call is blocked. In some embodiments, the unauthorized third party call is blocked by blocking the web page content associated with the unauthorized third party call from being written to the web page.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 13/476,439, entitled DATA COUNTER MEASURES filed May 21, 2012which is incorporated herein by reference for all purposes, which claimspriority to U.S. Provisional Application No. 61/487,866, entitled DATACOUNTER MEASURES filed May 19, 2011 which is incorporated herein byreference for all purposes.

BACKGROUND OF THE INVENTION

Online publishers often include third party content on their web pages.These third parties provide services that include, but are not limitedto: analytics, advertising, widgets that add functionality for endusers, and behavioral tracking These third party services typically areprovided at least in part by embedding onto a first party publisher'sweb pages a snippet of third party HTML and JavaScript code.

This HTML and JavaScript code, once executed, performs the functionalitythat the publisher originally intended, but may also bring in requests,such as data collection requests, that were not authorized by thepublisher, such as requests by and/or on behalf of unwanted thirdparties. These data collection requests can be in the form of images(most common), scripts, or iframes—theoretically any tag that creates anHTTP transaction. As an example, and without limitation, a first partypublisher's web page (for example, an Autos site that is used byconsumers to compare car prices) may include the follow HTML code froman authorized third party, in this case one associated with thefictional domain “3rdparty.com”:

<script src=“http://3rdparty.com/writePixel.js”></script>

However, writePixel.js in the above example may contain something likethe following:

document.write(‘<imgsrc=“http://blacklisted.com/?make=bmw&model=5-series&price=50000-70000”/>’);

In the above example, an authorized third party (“3rdparty”) hasincluded on the publisher's page a tag that results in a call notauthorized by the publisher being made out to a site associated with anunauthorized third party (“blacklisted”), which in this example resultsin user data being passed to the unauthorized third party, for examplecookie data stored on the user's computer. Using the data that is passedalong with the unauthorized call, the third party (“blacklisted.com”) isnow able to track that user as one being in-market for high-end luxurycars.

These unwanted requests may have unwanted affects, such as:

-   -   Devaluing the publishers online advertising inventory by making        their audience's data available to channels not controlled by        the publisher, ultimately decreasing revenue for the publisher.    -   Increasing web page load time for end users with additional HTTP        traffic. In addition to creating a poorer experience for end        users, this leads to lower revenue for the publisher when        end-users abandon sites or visit fewer pages because the web        pages are slow.    -   Compromising the privacy of the users by having their data        shared with unauthorized companies. With an evolving privacy        regime, unwarranted distribution of user's data is a big concern        for Publishers.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a flow diagram illustrating an embodiment of a process toblock unauthorized third party calls.

FIG. 2 is a block diagram illustrating an embodiment of a system toblock unauthorized third party calls.

FIG. 3 is a block diagram illustrating an embodiment of a web page inwhich a control tag has been embedded to block unauthorized third partycalls.

FIG. 4 is a flow diagram illustrating an embodiment of a process toconfigure a publisher's web pages to cause unauthorized third partycalls to be blocked.

FIG. 5 is a flow diagram illustrating an embodiment of a process toblock unauthorized third party calls.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Techniques to block unauthorized third party requests associated withcode associated with a first party publisher's web page are disclosed.In various embodiments, a data countermeasures platform is provided,which may include one or more of the components and features describedherein.

FIG. 1 is a flow diagram illustrating an embodiment of a process toblock unauthorized third party calls. In the example shown, anindication is received that third party code included on a first partypublisher's web page is attempting to write to the web page contentassociated with an unauthorized third party call (102). For example,third party JavaScript or other code included with authorization on thepublisher's web page may attempt to write to the web page as rendered bya client system's browser an element that would cause a call, such as anHTTP or other request, to be made out to an unauthorized third party,resulting in unauthorized transfer of user or other data to theunauthorized third party. In the example shown, the unauthorized thirdparty call is blocked (104). In some embodiments, the call is blocked bymodifying the content to be written to the web page in a manner thatresults in the client browser not making the unauthorized third partycall.

FIG. 2 is a block diagram illustrating an embodiment of a system toblock unauthorized third party calls. In the example shown, web users202 use the Internet 204 to access web pages 206 from a publisher orother web server 208. In the example shown, an unauthorized third party210 attempts to gather user data from and about web users 202 who viewthe publisher 208's web pages 206, e.g., to populate a user datadatabase 212. For example, the unauthorized third party may desire tosell to entities other than publisher 208 information about the onlinebehavior of web users 202 who have viewed publisher 208′s web pages 206.In the example shown, the publisher 208 uses a service provided via adata countermeasures server 214 and a configuration data store 216 toblock unauthorized calls from its web pages.

In various embodiments, a body of JavaScript and/or other code isprovided that, when included on the web page by the online publisher,examines requests as they come in from third parties. If the publisherhas disallowed requests from that particular party, for example, asindicated by data included in the configuration files 216, the requestis blocked. In some embodiments, the JavaScript and/or other codecomprises a “control tag” or other code that is provided to thepublisher to be embedded by the publisher in the publisher's web pages.

FIG. 3 is a block diagram illustrating an embodiment of a web page inwhich a control tag has been embedded to block unauthorized third partycalls. In the example shown, a publisher of web page 302 has embedded acontrol tag 304 in the web page.

In some embodiments, the control tag overrides the native behavior ofdocument.write, JavaScript's built in method for writing html to thepage. By intercepting calls to this function, the control tag buffersthe content being passed to it. The content is processed with an htmlprocessor, with a callback function called whenever an opening html tagis called. This callback function is called with a list of theattributes in the opening tag. The attributes of incoming tags areinspected, and compared against the allowed tags/attributes as specifiedby the publisher. If a disallowed third party call is found, the html isremoved and/or modified so that the browser does not execute it.

For example, if the 3rd party calls:

document.write(“<img src=”’+‘http://www.bl’+‘ocked.com/pixel.gif’>”)

The control tag will parse the html passed to document.write, resultingin:

<img src=‘http://www.blocked.com/pixel.gif’>

Before writing it to the page, the “src” (source) attribute will bechecked against the publisher's blacklisted domains. If the content isto be blocked, it will be modified so that the browser does not executeit, such as:

<img blockedsrc=‘http://www.blocked.com/pixel.gif’>

The control tag in some embodiments also overrides other native elementsthat may be used to create html on the page in the same manner, such asImage and document.createElement.

In various embodiments, publishers are provided a way, e.g., a web-basedadministrative interface, to select companies that are to be blocked,based in some embodiments on proprietary or other databases of onlinethird parties mapped to urls/domain names. In some embodiments, a datacounter measures service provider builds and maintains a database ofthird party companies that show up via HTTP requests on publisher pages.The database is keyed off of the domain portion of the URL. In variousembodiments one or both of human and automated processes as used topopulate the database. In some embodiments, third party companies arecategorized by their industry niche (or based on other attributes orcriteria), so that publishers understand what type of company they are,e.g., market research, ad serving, etc. Via an administrative console orother interface, the publisher can choose which companies and/or classesof company to disallow, and the lists of these companies and domainpatterns are delivered to the web page via a control tag or othermechanism, as described more fully herein. In some embodiments, use of acontrol tag embedded in a publisher's web page to retrieve and/or updateconfiguration at runtime allows for new third party companies, domains,etc. to be blocked within minutes.

FIG. 4 is a flow diagram illustrating an embodiment of a process toconfigure a publisher's web pages to cause unauthorized third partycalls to be blocked. In the example shown, a list of third partiesand/or classes of third parties that a particular publisher desires toblock is received (402), for example via a web-based or otheradministrative interface. Control tag code is provided to the publisher(404), who embeds the control tag in web pages desired to be protected.The control tag in various embodiments includes code to retrieve and/orupdate a list of blocked third parties, e.g., at runtime when a clientbrowser executes code comprising the control tag. A controltag-generated request for configuration file data for the publisher isreceived (406), and configuration file data is sent in response to thecontrol tag-generated request (408).

In various embodiments, unwanted requests are blocked by taking controlof how a web browser writes content to the page (via Javascript'sdocument.write in some embodiments) and changing its behavior so thatincoming content can be inspected before it is executed. In variousembodiments, the native behavior of one or more of JavaScript'sdocument.createElement, Image tag, and other functions that allow forunauthorized HTTP transactions to be performed are overwritten tointercept, detect, and block unauthorized third party calls. Byprocessing HTML as it is being written to a web page, and using a hookmechanism to call out to a data counter measures module or other entityevery time a new tag is written to the page, tags can be inspected forvalidity before they are written.

FIG. 5 is a flow diagram illustrating an embodiment of a process toblock unauthorized third party calls. In some embodiments, the processof FIG. 5 is implemented by a control tag and/or associated code. In theexample shown, a JavaScript or other script runtime's document and/orother content writing function(s) is/are overwritten (502), e.g., toenable the writing of content that may otherwise result in anunauthorized call (e.g., an HTTP or other request) to be detected andblocked. A configuration file and/or other source of a list of blockedthird parties is retrieved and processed (504). As the page isprocessed, upon encountering an open tag (506) the tag is parsed toextract attributes (508), e.g., the “src” or other content sourceattribute. If a relevant attribute is associated with a third party onthe publisher's list of third parties to block (510), actions areperformed to block the call from being made to the third party (512),such as by modifying data comprising the tag to cause the browser not tomake the unauthorized third party call. Processing of the web pagecontinues in this way until no other tags remain to be processed (514).

In some embodiments, an optional reporting component is made available.Every time a request is blocked, a reporting call is sent back to a datacounter measures service provider or other reporting destination, sothat data can be gathered, aggregated, summarized and displayed to thepublisher, so they may know how many requests where blocked.

Techniques to intercept and block HTTP requests, e.g., by checkingcontent before it is written to the page, have been disclosed. Analternative approach would be to remove the unwanted content from theweb page after it has been downloaded, but by this time the HTTP requesthas already been sent to the unwanted party, passing along the end-userscookie information, which may be part of what the publisher wanted toblock.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A method of blocking unwanted calls, comprising:obtaining an indication that a first code included on a web page isattempting a third party call to a web server; determining that the webserver is an unauthorized third party; and at least partially inresponse to determining that the web server is an unauthorized thirdparty, blocking the third party call, at least in part by causing thebrowser not to execute the third party call.
 2. The method of claim 1,wherein the indication indicates that the first code is attempting towrite, to the web page, content associated with the third party call. 3.The method of claim 2, wherein the obtaining of the indication that thefirst code included on the web page is attempting to write contentassociated with the third party content comprises: intercepting thethird party call from the first code included on the web page to the webserver at least in part by overriding, by a control tag included in asecond code of the web page, a behavior of a content writing functionassociated with the web page and inspecting the content before thecontent is written to the web page.
 4. The method of claim 3, whereinthe intercepting of the third party call includes intercepting a call toa function to write content to the web page.
 5. The method of claim 4,wherein determining that the third party call is to an unauthorizedthird party includes parsing the call to determine a called sourceattribute.
 6. The method of claim 5, wherein determining that the thirdparty call is to an unauthorized third party further includesdetermining that the called source attribute is associated with theunauthorized third party.
 7. The method of claim 6, wherein determiningthat the called source attribute is associated with the unauthorizedthird party includes comparing the called source attribute to a list ofdomains associated with one or more unauthorized third parties.
 8. Themethod of claim 1, wherein the browser is caused to not execute thethird party call by modifying data comprising a tag.
 9. The method ofclaim 1, wherein blocking the third party call comprises blockingcontent associated with the unauthorized third party from being writtento the web page.
 10. The method of claim 2, wherein the contentassociated with the unauthorized third party is blocked from beingwritten to the web page at least in part by replacing the contentassociated with the unauthorized third party with other content notassociated with any unauthorized third party.
 11. The method of claim 1,wherein the third party call comprises a hypertext transfer protocol(HTTP) request.
 12. The method of claim 1, wherein the first codeincluded on the web page comprises hypertext markup language (HTML)code.
 13. The method of claim 1, wherein the first included on the webpage comprises JavaScript code.
 14. The method of claim 1, wherein thefirst code included on the web page comprises code that invokes afunction to write content to the web page.
 15. The method of claim 1,wherein the first code included on the web page comprises JavaScriptcode that invokes a document.write function of JavaScript.
 16. Themethod of claim 1, further comprising receiving, from a first partypublisher associated with the web page, a second indication that theunauthorized third party is unauthorized.
 17. The method of claim 16,wherein receiving from the first party publisher the second indicationthat the unauthorized third party is unauthorized includes receivingfrom the first party publisher an indication that the first partypublisher desires to block third party calls associated with a class ofthird party with which the unauthorized third party is-associated. 18.The method of claim 1, wherein the third party call includes user data.19. The method of claim 1, wherein determining that the third party callis to the unauthorized third party comprises: updating, using a controltag included in code of the web page, a list of unauthorized thirdparties; extracting a domain attribute from a tag associated with thethird party call; and determining that the domain attribute extractedfrom the tag is associated with the unauthorized third party in the listof unauthorized third parties.
 20. The method of claim 19, whereinextracting the domain attribute comprises: identifying an open tagincluded in the tag associated with the third party call; parsing thetag to identify the domain attribute; and extracting the domainattribute.
 21. The method of claim 1, further comprising: reporting theblocking of the third party call to a publisher of the web page.
 22. Themethod of claim 21, wherein the reporting of the blocking of the thirdparty call includes sending information associated with the blocking ofthe third party call to a data counter measures service provider.
 23. Asystem to block unwanted calls, comprising: a processor configured to:obtain an indication that a first code included on a web page isattempting a third party call to a web server; determine that the webserver is to an unauthorized third party; and at least partially inresponse to determining that the web server is an unauthorized thirdparty, block the third party call, at least in part by causing thebrowser not to execute the third party call; and a memory coupled to theprocessor and configured to provide the processor with instructions. 24.The system of claim 23, wherein to block third party call the processoris further configured to block content associated with the unauthorizedthird party from being written to the web page.
 25. The system of claim24, wherein the content associated with the unauthorized third party isblocked from being written to the web page at least in part by replacingthe content associated with the unauthorized third party with othercontent not associated with any unauthorized third party.
 26. The systemof claim 23, wherein the third party call comprises a hypertext transferprotocol (HTTP) request.
 27. The system of claim 23, wherein to obtainthe indication the processor is further configured to intercept thethird party call from the first code included on the web page to the webserver at least in part by overriding, by a control tag included in asecond code of the web page, a behavior of a content writing functionassociated with the web page and inspecting the content before thecontent is written to the web page.
 28. A computer program product toblock unwanted calls, the computer program product being embodied in atangible, non-transitory computer readable storage medium and comprisingcomputer instructions for: obtaining an indication that a first codeincluded on a web page is attempting a third party call to a web server;determining that the web server is an unauthorized third party; and atleast partially in response to determining that the web server is anunauthorized third party, blocking the third party call, at least inpart by causing the browser not to execute the third party call.
 29. Thecomputer program product of claim 28, wherein the indication indicatesthat the first code is attempting to write, to the web page, contentassociated with the third party call.
 30. The computer program productof claim 28, wherein the obtaining of the indication that the first codeincluded on the web page is attempting to write content associated withthe third party content comprises: intercepting the third party callfrom the first code included on the web page to the web server at leastin part by overriding, by a control tag included in a second code of theweb page, a behavior of a content writing function associated with theweb page and inspecting the content before the content is written to theweb page.
 31. The computer program product of claim 30, wherein theintercepting of the third party call includes intercepting a call to afunction to write content to the web page
 32. The computer programproduct of claim 28, wherein blocking the third party call comprisesblocking content associated with the unauthorized third party from beingwritten to the web page.
 33. The computer program product of claim 32,wherein the content associated with the unauthorized third party isblocked from being written to the web page at least in part by replacingthe content associated with the unauthorized third party with othercontent not associated with any unauthorized third party.
 34. Thecomputer program product of claim 28, wherein the first code included onthe web page comprises code that invokes a function to write content tothe web page.